Skip to contentSkip to conversation

Yocto Porject

DISCUSSION Scott Rifenbark 2 participants 2 messages Jan 28, 2019 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Hi Don,

I can't really advise you on this as I am not a Yocto developer. However, I can forward this question to the [email protected] mail group and, in particular, to a resource that is looking closely at kernel stuff to help improve that manual and get it more up-to-date. That guy is named Richard Griffiths of Intel. You should be able to get some help with this. Sorry... I wish I was a crack YP developer :)

Thanks,
Scott

Quoted 116 lines · Don Osmond

Scott

I have been reading your
https://www.yoctoproject.org/docs/2.4/kernel-dev/kernel-dev.html and it has been very helpful. I have a project where I am needing to get the ability to use iptables NAT which does not come in the core image from Digi which also uses Yocto. In my Ubuntu 16.04 LTS development VM, I am able to build the base image (bitbake dey-image-qt), menuconfig the kernel config (bitbake -c devshell virtual/kernel), compile the kernel (bitbake -C compile virtual/kernel). The results are in the /workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc as see in list below:

dosmond@ubuntu:/workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc$ ls

boot.scr

dey-image-qt-x11-ccimx6ulsbc-20190127164412.boot.ubifs

dey-image-qt-x11-ccimx6ulsbc-20190127164412.recovery.ubifs

dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.manifest

dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.tar.bz2

dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.ubifs

dey-image-qt-x11-ccimx6ulsbc-20190127164412.testdata.json

dey-image-qt-x11-ccimx6ulsbc.boot.ubifs

dey-image-qt-x11-ccimx6ulsbc.manifest

dey-image-qt-x11-ccimx6ulsbc.recovery.ubifs

dey-image-qt-x11-ccimx6ulsbc.tar.bz2

dey-image-qt-x11-ccimx6ulsbc.testdata.json

dey-image-qt-x11-ccimx6ulsbc.ubifs

dey-image-recovery-initramfs-ccimx6ulsbc-20190127161551.rootfs.cpio.gz.u-boot.tf

dey-image-recovery-initramfs-ccimx6ulsbc-20190127161551.rootfs.manifest

dey-image-recovery-initramfs-ccimx6ulsbc-20190127161551.testdata.json

dey-image-recovery-initramfs-ccimx6ulsbc.cpio.gz.u-boot.tf

dey-image-recovery-initramfs-ccimx6ulsbc.manifest

dey-image-recovery-initramfs-ccimx6ulsbc.testdata.json

imx6ul-ccimx6ulsbc.dtb

imx6ul-ccimx6ulsbc-id135.dtb

imx6ul-ccimx6ulsbc-id136.dtb

imx6ul-ccimx6ulsbc-wb.dtb

install_linux_fw_sd.scr

modules--4.9-r0.5-ccimx6ulsbc-20190127182701.tgz

modules-ccimx6ulsbc.tgz

u-boot-ccimx6ulsbc1GB-2017.03-r0.imx

u-boot-ccimx6ulsbc1GB.imx

u-boot-ccimx6ulsbc-2017.03-r0.imx

u-boot-ccimx6ulsbc.imx

u-boot-ccimx6ulsbc.imx-ccimx6ulsbc

u-boot-ccimx6ulsbc.imx-ccimx6ulsbc1GB

u-boot.imx

zImage

zImage--4.9-r0.5-ccimx6ulsbc-20190127182701.bin

zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-20190127182701.dtb

zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id135-20190127182701.dtb

zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id136-20190127182701.dtb

zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-wb-20190127182701.dtb

zImage-ccimx6ulsbc.bin

zImage-imx6ul-ccimx6ulsbc.dtb

zImage-imx6ul-ccimx6ulsbc-id135.dtb

zImage-imx6ul-ccimx6ulsbc-id136.dtb

zImage-imx6ul-ccimx6ulsbc-wb.dtb

So, what I am having an issue with are the steps to get the latest kernel changes a part of the image? I thought if I ran “bitbake dey-image-qt” again that it would. I think I am missing something. Anything you can share would be greatly appreciated.

Thanks

Don

#2 lore raw
Quoted 10 lines · Scott Rifenbark

Hi Don,

I can't really advise you on this as I am not a Yocto developer. However, I can forward this question to the [email protected] mail group and, in particular, to a resource that is looking closely at kernel stuff to help improve that manual and get it more up-to- date.  That guy is named Richard Griffiths of Intel.  You should be able to get some help with this.  Sorry... I wish I was a crack YP developer :)

Quoted 74 lines

Thanks,
Scott

Quoted 69 lines · Don Osmond

Scott
I have been reading your https://www.yoctoproject.org/docs/2.4/kern
el-dev/kernel-dev.html and it has been very helpful.  I have a project where I am needing to get the ability to use iptables NAT which does not come in the core image from Digi which also uses Yocto.  In my Ubuntu 16.04 LTS development VM, I am able to build the base image (bitbake dey-image-qt), menuconfig the kernel config (bitbake -c devshell virtual/kernel), compile the kernel (bitbake -C compile virtual/kernel).  The results are in the /workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc as see in list below:
dosmond@ubuntu:/workspace/ccimx6ulsbc/tmp/deploy/images/ccimx6ulsbc

$ ls
boot.scr
dey-image-qt-x11-ccimx6ulsbc-20190127164412.boot.ubifs
dey-image-qt-x11-ccimx6ulsbc-20190127164412.recovery.ubifs
dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.manifest
dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.tar.bz2
dey-image-qt-x11-ccimx6ulsbc-20190127164412.rootfs.ubifs
dey-image-qt-x11-ccimx6ulsbc-20190127164412.testdata.json
dey-image-qt-x11-ccimx6ulsbc.boot.ubifs
dey-image-qt-x11-ccimx6ulsbc.manifest
dey-image-qt-x11-ccimx6ulsbc.recovery.ubifs
dey-image-qt-x11-ccimx6ulsbc.tar.bz2
dey-image-qt-x11-ccimx6ulsbc.testdata.json
dey-image-qt-x11-ccimx6ulsbc.ubifs
dey-image-recovery-initramfs-ccimx6ulsbc-
20190127161551.rootfs.cpio.gz.u-boot.tf
dey-image-recovery-initramfs-ccimx6ulsbc-
20190127161551.rootfs.manifest
dey-image-recovery-initramfs-ccimx6ulsbc-
20190127161551.testdata.json
dey-image-recovery-initramfs-ccimx6ulsbc.cpio.gz.u-boot.tf
dey-image-recovery-initramfs-ccimx6ulsbc.manifest
dey-image-recovery-initramfs-ccimx6ulsbc.testdata.json
imx6ul-ccimx6ulsbc.dtb
imx6ul-ccimx6ulsbc-id135.dtb
imx6ul-ccimx6ulsbc-id136.dtb
imx6ul-ccimx6ulsbc-wb.dtb
install_linux_fw_sd.scr
modules--4.9-r0.5-ccimx6ulsbc-20190127182701.tgz
modules-ccimx6ulsbc.tgz
u-boot-ccimx6ulsbc1GB-2017.03-r0.imx
u-boot-ccimx6ulsbc1GB.imx
u-boot-ccimx6ulsbc-2017.03-r0.imx
u-boot-ccimx6ulsbc.imx
u-boot-ccimx6ulsbc.imx-ccimx6ulsbc
u-boot-ccimx6ulsbc.imx-ccimx6ulsbc1GB
u-boot.imx
zImage
zImage--4.9-r0.5-ccimx6ulsbc-20190127182701.bin
zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-20190127182701.dtb
zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id135-20190127182701.dtb
zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-id136-20190127182701.dtb
zImage--4.9-r0.5-imx6ul-ccimx6ulsbc-wb-20190127182701.dtb
zImage-ccimx6ulsbc.bin
zImage-imx6ul-ccimx6ulsbc.dtb
zImage-imx6ul-ccimx6ulsbc-id135.dtb
zImage-imx6ul-ccimx6ulsbc-id136.dtb
zImage-imx6ul-ccimx6ulsbc-wb.dtb
 
So, what I am having an issue with are the steps to get the latest
kernel changes a part of the image?  I thought if I ran “bitbake
dey-image-qt” again that it would.  I think I am missing
something.  Anything you can share would be greatly appreciated.
Thanks
Don

Hi Don,
Are you asking how do you save changes to your kernel configuration so they become part of the kernel recipe? If so, the
2.2.3 Changing The Configuration section of the Kernel Dev manual gives an example.
If that is not what you're asking, please clarify and I will do my best to help.
Regards,
Richard